URLs Field Capabilities |
Standard Capabilities |
http://
, ftp://
and mailto:
protocols are defined, but KeePass supports
all registered protocols which the Internet Explorer supports.ssh://
URLs,
KeePass will automatically use PuTTY for ssh://
URLs, too. KeePass uses the same
settings as Windows and Internet Explorer do.Executing command-lines |
cmd://
. If you would like to execute
Notepad, your URL could look like this:cmd://
protocol also supports parameters for executed
applications, in contrast to
the file://
protocol. This was the main reason why cmd://
was introduced, with file://
you
aren't able to pass any parameters to started applications. Use the cmd://
protocol instead.cmd://
protocol don't need to be encoded. For example,
you do not have to replace space characters by %20
, as it is normally
required for other URLs. KeePass just cuts away the cmd://
virtual
protocol prefix and passes the remaining command-line to Windows.Substitutions |
Field | Code |
Title field | {TITLE} or %TITLE% |
Username field | {USERNAME} or %USERNAME% |
URL field | {URL} or %URL% |
Password field | {PASSWORD} or %PASSWORD% |
Notes field | {NOTES} or %NOTES% |
Current application directory path | {APPDIR} or %APPDIR% |
{APPDIR}
and %APPDIR%
substitution codes are replaced by the application
directory path of the currently running KeePass instance. It's the full absolute path of the
directory containing the KeePass executable, without a trailing backslash.
If you would like to start a new KeePass instance, you could set the URL to: